- MatrixAndQuaternionsFaq . . . . 92 matches
Q3. How do I represent a matrix using the C/C++ programming languages?
Q5. How do matrices relate to coordinate systems?
Q9. How do I add two matrices together?
Q10. How do I subtract two matrices?
Q11. How do I multiply two matrices together?
Q12. How do I square or raise a matrix to a power?
Q13. How do I multiply one or more vectors by a matrix?
Q15. How do I calculate the determinant of a matrix?
Q18. How do I calculate the inverse of an arbitary matrix?
Q19. How do I calculate the inverse of an identity matrix?
Q20. How do I calculate the inverse of a rotation matrix?
Q21. How do I calculate the inverse of a matrix using Kramer's rule?
Q22. How do I calculate the inverse of a 2x2 matrix?
Q23. How do I calculate the inverse of a 3x3 matrix?
Q24. How do I calculate the inverse of a 4x4 matrix?
Q25. How do I calculate the inverse of a matrix using linear equations?
Q27. How do I generate a rotation matrix in the X-axis?
Q28. How do I generate a rotation matrix in the Y-axis?
Q29. How do I generate a rotation matrix in the Z-axis?
Q32. How do I combine rotation matrices?
- HowManyZerosAndDigits/임인택 . . . . 33 matches
private HowManyZerosAndDigits object;
object = new HowManyZerosAndDigits(0, 0);
public void testHowManyZeros() {
object = new HowManyZerosAndDigits(0, 0);
assertEquals(0, object.howManyZeros(1));
assertEquals(1, object.howManyZeros(10));
assertEquals(2, object.howManyZeros(100));
assertEquals(2, object.howManyZeros(1010));
// object = new HowManyZerosAndDigits(120, 16);
// object = new HowManyZerosAndDigits(120, 10);
== {{{~cpp HowManyZerosAndDigits.java }}} ==
public class HowManyZerosAndDigits {
public HowManyZerosAndDigits(int n, int b) {
System.out.println(howManyZeros() + " " + numDigit());
public int howManyZeros(long num) {
public int howManyZeros() {
return howManyZeros((long)_fact);
count += howManyZeros(l.longValue());
HowManyZerosAndDigits h = new HowManyZerosAndDigits(n, b);
[HowManyZerosAndDigits]
- HowManyFibs?/황재선 . . . . 20 matches
public int howManyFib(BigInteger start, BigInteger end) {
int howMany = 0;
howMany = 2;
howMany = 1;
howMany++;
return howMany;
public void printNumOfFibs(int numOfFibs) {
System.out.println(numOfFibs);
int numOfFibs = fib.howManyFib(start, end);
fib.printNumOfFibs(numOfFibs);
assertEquals(5, fib.howManyFib(new BigInteger("10"), new BigInteger("100")));
assertEquals(4, fib.howManyFib(new BigInteger("1234567890"),
assertEquals(1, fib.howManyFib(new BigInteger("1"), new BigInteger("1")));
assertEquals(1, fib.howManyFib(new BigInteger("0"), new BigInteger("1")));
[HowManyFibs?]
- MoreEffectiveC++/Techniques1of3 . . . . 16 matches
class TooManyObjects{}; // 너무 많은 객체를 요구하면
이런 아이디어는 numObject를 사용해서 Printer객체의 수를 제한 시켜 버리는 것이다. 위에도 언급하였듯이 객체의 수가 1개를 초과하면, TooManyObject 예외를 발생시킨다.
throw TooManyObjects();
첫번째 객체 p는 순조로히 생성된다. 하지만 엄연히 다른 프린터를 대상으로 하고 있는 cp는 생성되지 않고, TooManyObjects 예외를 발생 시킨다. 왜 그러는지 모두들 예상 할것이다. 더불어 비슷 또 다른 경우를 생각 해 본다면.
CPFMachine m2; // TooManyObjects 예외를 발생 시킨다.
class TooManyObjects{};
throw TooManyObjects();
class TooManyObjects{};
throw TooManyObjects();
throw TooManyObjects();
class TooManyObjects{}; // 던질 예외
if (numObjects >= maxObjects) throw TooManyObjects();
해당 클래스는 오직 기본 클래스로만 쓰이도록 설계되어 졌다. 그러므로, 생성자와 파괴자가 모두 protected(보호)인자로 설정되어 있다. 그리고 init로서 object-counting을 구현한다. init는 설정된 객체의 숫자가 넘어가면, TooManyObjects 예외 객체를 발생 시킨다.
using Counted<Printer>::TooManyObjects; // 마찬가지~
이는 using이 존재 하지 않았을때 사용된 옛날 문법이다. TooManyObjects 클래스 역시 같은 이유로 using을 이용해서 이름을 사용하게 권한을 열었으며, 이렇게 TooManyObjects를 허용해야 지만 해야지만 클라이언트들이 해당 예외를 잡을 수 있다.
- Celfin's ACM training . . . . 15 matches
|| 9 || 6 || 110602/10213 || How Many Pieces Of Land? || 3 hours || [http://165.194.17.5/wiki/index.php?url=zeropage&no=4143&title=HowManyPiecesOfLand?/하기웅&login=processing&id=celfin&redirect=yes How Many Pieces Of Land?/Celfin] ||
|| 10 || 6 || 110601/10183 || How Many Fibs? || 2 hours || [http://165.194.17.5/wiki/index.php?url=zeropage&no=4172&title=HowManyFibs?/하기웅&login=processing&id=celfin&redirect=yes How Many Fibs?/Celfin] ||
|| 24 || 1 || 110105/10267 || Graphical Editor || many days || [Graphical Editor/Celfin] ||
|| 29 || 2 || 110202/10315 || Poker Hands || many days || [PokerHands/Celfin] ||
- HowManyFibs? . . . . 15 matches
=== About [HowManyFibs?] ===
|| 황재선 || Java || 1h || [HowManyFibs?/황재선] ||
|| 문보창 || C++ || 2h || [HowManyFibs?/문보창] ||
|| [1002] || Python || 1차: 3시간(실패), 2차: 10분 || [HowManyFibs?/1002] ||
|| 하기웅 || C++ || 2h || [HowManyFibs?/하기웅] ||
- HowManyZerosAndDigits . . . . 10 matches
== About[HowManyZerosAndDigits] ==
|| [문보창] || C++ || ? || [HowManyZerosAndDigits/문보창] ||
|| [임인택] || Java || ? || [HowManyZerosAndDigits/임인택] [[BR]] 주의 : 일단 10진법 이상의 진법도 10진수로 표현한다고 가정하고 문제를 풀었음 [[BR]] (예를 들어 A0 대신 10 0 이라고 표현한다고 가정) ||
|| [김회영] || C++ || ? || [HowManyZerosAndDigits/김회영] ||
|| [허아영] || C++ || 1시간 30분 || [HowManyZerosAndDigits/허아영] ||
- MoinMoinFaq . . . . 10 matches
very many pages, which describe various projects, architectures,
=== How does this compare to other collaboration tools, like Notes? ===
==== How can I search the wiki? ====
* Click on TitleIndex. This will show you an alphabetized list
* Click on WordIndex. This shows an alphabetized list of every
* Click on {{{~cpp LikePages}}} at the bottom of the page. This shows pages
shows what pages link to the current page (which may help you
==== How do I see what's been going on recently in the wiki? ====
Any mixed case name that doesn't have a page will show up as a red link.
==== How do add something to the wiki, or change something that's wrong? ====
Not very many. It helps to keep certain types of information
The wiki has a feature called "Templates" which show up when you
==== How can I add non-text information to the Wiki? ====
==== How do I add an image to a page? ====
However, in some cases it may be appropriate to just make your change
This would show up on the page as:
=== How do I activate the "DeletePage" option? ===
=== How do I administer the wiki? ===
=== How do I create a new Template page? ===
Templates are pages that show up automatically as options when you
- ProgrammingWithInterface . . . . 10 matches
public void pushMany(Object[] articles) {
public void pushMany(Object [] articles) {
깔끔한 코드가 나왔다. 하지만 MonitorableStack은 pushMany 함수를 상속한다. MonitorableStack을 사용해 pushMany 함수를 호출하면 MonitorableStack의 입력 받은 articles의 articles.length 만큼 push가 호출된다. 하지만 지금 호출된 push 메소드는 MonitorableStack의 것이라는 점! 매번 size() 함수를 호출해 최대 크기를 갱신한다. 속도가 느려질 수도 있다. 그리고 만약 누군가 Stack의 코드를 보고 pushMany 함수의 비 효율성 때문에 Stack을 밑의 코드와 같이 수정했다면 어떻게 될 것인가???
public void pushMany(Object [] articles) {
와!~ 예전의 Stack보다 성능은 확실히 좋아 졌을 것이다. 그런데 문제가 발생했다. 더이상 pushMany 메소드에서 push 메소드를 호출하지 않는다. 이렇게 되면 MonitorableStack은 더이상 Stack의 최대 크기를 추적하지 못하게 된다. 예기치 않은 결과이다. 상속을 사용한 구현으로 발생한 문제이다. 여기까지 글을 (책의 내용) 읽었다면, 아마 '상속을 사용하기 전에 한번 더 생각하는게 좋겠다' 라는 생각을 가슴 깊이 느꼈을 것이다. 아니면 별수 없는 일이다... :(
void pushMany(Object [] articles);
public void pushMany(Object [] articles) {
public void pushMany(Object [] articles) {
- 데블스캠프2011/다섯째날/HowToWriteCodeWell . . . . 7 matches
* [데블스캠프2011/다섯째날/How To Write Code Well/송지원, 성화수]
* [데블스캠프2011/다섯째날/How To Write Code Well/권순의, 김호동]
* [데블스캠프2011/다섯째날/How To Write Code Well/김준석, 서영주]
* [데블스캠프2011/다섯째날/How To Write Code Well/정의정, 김태진]
* [데블스캠프2011/다섯째날/How To Write Code Well/임상현, 서민관]
* [데블스캠프2011/다섯째날/How To Write Code Well/강소현, 구자경]
* [데블스캠프2011/다섯째날/How To Write Code Well/박정근, 김수경]
- 1002/Journal . . . . 6 matches
도서관에서 이전에 절반정도 읽은 적이 있는 Learning, Creating, and Using Knowledge 의 일부를 읽어보고, NoSmok:HowToReadaBook 원서를 찾아보았다. 대강 읽어봤는데, 전에 한글용어로는 약간 어색하게 느껴졌던 용어들이 머릿속에 제대로 들어왔다. (또는, 내가 영어로 된 책을 읽을때엔 전공책의 그 어투를 떠올려서일런지도 모르겠다. 즉, 영어로 된 책은 약간 더 무겁게 읽는다고 할까. 그림이 그려져 있는 책 (ex : NoSmok:AreYourLightsOn, 캘빈 & 홉스) 는 예외)
책을 읽으면서 '해석이 안되는 문장' 을 그냥 넘어가버렸다. 즉, NoSmok:HowToReadaBook 에서의 첫번째 단계를 아직 제대로 못하고 있는 것이다. 그러한 상황에서는 Analyicial Reading 을 할 수가 없다.
* 그렇다면, 어떻게 NoSmok:HowToReadaBook 이나 'Learning, Creating, and Using Knowledge' 은 읽기 쉬웠을까?
* 사전지식이 이미 있었기 때문이라고 판단한다. NoSmok:HowToReadaBook 는 한글 서적을 이미 읽었었고, 'Learning, Creating, and Using Knowledge' 의 경우 Concept Map 에 대한 이해가 있었다. PowerReading 의 경우 원래 표현 자체가 쉽다.
* 처음 프로그래밍을 접하는 사람에게는 전체 프로젝트 과정을 이해할 수 있는 하루를, (이건 RT 보단 밤새기 프로젝트 하루짜리를 같이 해보는게 좋을 것 같다.) 2-3학년때는 중요 논문이나 소프트웨어 페러다임 또는 양서라 불리는 책들 (How To Read a Book, 이성의 기능, Mind Map 이나 Concept Map 등)을 같이 읽고 적용해보는 것도 좋을것 같다.
mainFrame.show ();
mainFrame.show ();
* 학교에서 레포트를 쓰기 위해 (["ProgrammingLanguageClass/Report2002_2"]) 도서관에 들렸다. HowToReadIt 의 방법중 다독에 관한 방법을 떠올리면서 약간 비슷한 시도를 해봤다. (오. 방법들 자체가 Extreme~ 해보인다;) 1시간 30분 동안 Java 책 기초서 2권과 원서 1권, VB책 3권정도를 훑어읽었다. (10여권까지는 엄두가 안나서; 도서관이 3시까지밖에 안하는 관계로) 예전에 자바를 하긴 했었지만, 제대로 한 기억은 없다. 처음에는 원서와 고급서처럼 보이는 것을 읽으려니까 머리에 잘 안들어왔다. 그래서 가장 쉬워보이는 기초서 (알기쉬운 Java2, Java2 자바토피아 등 두께 얇은 한서들) 를 읽고선 읽어가니까 가속이 붙어서 읽기 쉬웠다. 3번째쯤 읽어나가니까 Event Listener 의 Delegation 의 의미를 제대로 이해한 것 같고 (예전에는 소스 따라치기만 했었다.) StatePattern으로의 진화 (진화보단 '추후적응' 이 더 맞으려나) 가 용이한 구조일 수 있겠다는 생각을 하게 되었다. (Event Listener 에서 작성했던 코드를 조금만 ["Refactoring"] 하면 바로 StatePattern 으로 적용을 시킬 수 있을 것 같다는 생각이 들었다. 아직 구현해보진 않았기 때문에 뭐라 할말은 아니지만.) 시간이 있었다면 하루종일 시도해보는건데 아쉽게도 학교에 늦게 도착해서;
- ClassifyByAnagram/인수 . . . . 6 matches
MCI howManyEachAlphabet;
howManyEachAlphabet[ str[i] ] += 1;
_anagramTable[str] = howManyEachAlphabet;
void Show()
anagram.Show();
MCI howManyEachAlphabet;
howManyEachAlphabet[ str[i] ] += 1;
return howManyEachAlphabet;
void ShowAnagram()
ana.ShowAnagram();
- HowManyPiecesOfLand? . . . . 6 matches
=== About [HowManyPiecesOfLand?] ===
|| 문보창 || C++ || 7시간 || [HowManyPiecesOfLand?/문보창] ||
|| 하기웅 || C++ || 3시간 || [HowManyPiecesOfLand?/하기웅] ||
- 경시대회준비반 . . . . 6 matches
|| [HowManyFibs?] ||
|| [HowManyPiecesOfLand?] ||
|| [HowBigIsIt?] ||
- 데블스캠프2011 . . . . 6 matches
|| 5 || [변형진] || [:데블스캠프2011/첫째날/개발자는무엇으로사는가 개발자는 무엇으로 사는가] || [김동준] || [:데블스캠프2011/둘째날/Cracking Cracking - 창과 방패] || [김준석] || [:데블스캠프2011/셋째날/RUR-PLE RUR-PLE] || [이승한] || [:데블스캠프2011/넷째날/Git Git-분산 버전 관리 시스템] || [변형진] || [:데블스캠프2011/다섯째날/HowToWriteCodeWell How To Write Code Well] || 12 ||
|| 7 || [송지원] || [:데블스캠프2011/첫째날/Java Play with Java] || [:상협 남상협] || [:데블스캠프2011/둘째날/Machine-Learning Machine-Learning] || [윤종하], [황현] || [:데블스캠프2011/셋째날/Esolang 난해한 프로그래밍 언어] || [이승한] || [:데블스캠프2011/넷째날/Git Git-분산 버전 관리 시스템] || [변형진] || [:데블스캠프2011/다섯째날/HowToWriteCodeWell How To Write Code Well] || 2 ||
|| 8 || [송지원] || [:데블스캠프2011/첫째날/Java Play with Java] || [:상협 남상협] || [:데블스캠프2011/둘째날/Machine-Learning Machine-Learning] || [윤종하], [황현] || [:데블스캠프2011/셋째날/Esolang 난해한 프로그래밍 언어] || [서지혜] || [:데블스캠프2011/넷째날/루비 루비] || [변형진] || [:데블스캠프2011/다섯째날/HowToWriteCodeWell How To Write Code Well] || 3 ||
- 컴퓨터공부지도 . . . . 6 matches
'What' 의 영역과 & 'How' 의 영역.
See Also HowToStudyXp, HowToReadIt, HowToStudyDataStructureAndAlgorithms, HowToStudyDesignPatterns, HowToStudyRefactoring
- AOI/2004 . . . . 5 matches
|| [HowManyZerosAndDigits] || . || O || X || . || . || . ||
|| [HowManyFibs?] || . || . || X || . || . || . || . || . ||
- HowManyFibs?/문보창 . . . . 5 matches
// 10183 - How many Fibs?
[HowManyFibs?]
- SeminarHowToProgramIt . . . . 5 matches
애들러의 How to Read a Book과 폴리야의 How to Solve it의 전통을 컴퓨터 프로그래밍 쪽에서 잇는 세미나가 2002년 4월 11일 중앙대학교에서 있었다.
see also SeminarHowToProgramItAfterwords
* Coding Style -- esp. How to Name it (프로그래머를 위한 정명학. "子曰 必也正名乎...名不正則言不順 言不順則事不成" <논어> 자로편)
* Managing To Do List -- How to Become More Productive Only With a To-do List While Programming
- django/Model . . . . 5 matches
employees= models.ManyToManyField(Employee)
Upload:Screenshot-ManyToOne.png
Upload:Screenshot-ManyToMany.png
- 서지혜 . . . . 5 matches
* 엔포지 : [http://nforge.zeropage.org/projects/bigtablet/wiki/FrontPage?action=show 빅테이블 분석및설계]
* [http://nforge.zeropage.org/projects/deletewastes/wiki/FrontPage?action=show 엔포지 링크]
* 디버거를 사용할 수 없는 환경을 난생 처음 만남. print문과 로그만으로 디버깅을 할 수 있다는 것을 깨달았다. 정보 로그, 에러 로그를 분리해서 에러로그만 보면 편하다. 버그가 의심되는 부분에 printf문을 삽입해서 값의 변화를 추적하는 것도 효과적이다(달리 할수 있는 방법이 없다..). 오늘 보게된 [http://wiki.kldp.org/wiki.php/HowToBeAProgrammer#s-3.1.1 HowToBeAProgrammer]에 이 내용이 올라와있다!! 이럴수가 난 삽질쟁이가 아니었음. 기쁘다.
* [HowToStudyDesignPatterns]
* [HowToStudyRefactoring]
* [HowToStudyRefactoring]
- DPSCChapter1 . . . . 4 matches
Smalltalk experts know many things that novices do not, at various abstraction levels and across a wide spectrum of programming and design knowledge and skills:
* How to use the specific tools of the Smalltalk interactive development environment to find and reuse existing functionality for new problems, as well as understanding programs from both static and runtime perspective
* How to define and implement behavior in new classes and where these classes ought to reside in the existing class hierarchy
A '''design pattern''' is a reusable implementation model or architecture that can be applied to solve a particular recurring class of problem. The pattern sometimes describes how methods in a single class or subhierarchy of classes work together; more often, it shows how multiple classes and their instances collaborate. It turns out that particular architectures reappear in different applications and systems to the extent that a generic pattern template emerges, one that experts reapply and customize to new application - and domain-specific problems. Hence, experts know how to apply design patterns to new problems to implement elegant and extensible solutions.
This book is designed to be a companion to ''Design Patterns'', but one written from the Smalltalk perspective. One way to think of the ''Smalltalk Companion'', then, is as a variation on a theme. We provide the same pattern as in the Gang of Four book but view them through Smalltalk glasses. (In fact, when we were trying out names for the ''Smalltalk Companion'', someone suggested "DesignPattern asSmalltalkCompanion." However, we decided only hard-core Smalltalkers would get it.)
But the ''Smalltalk Companion'' goes beyond merely replicating the text of ''Design Patterns'' and plugging in Smalltalk examples whereever C++ appeared. As a result, there are numerous situations where we felt the need for additional analysis, clarification, or even minor disagreement with the original patterns. Thus, many of our discussions should apply to other object-oriented languages as well.
* Many new examples, from application domains(insurance, telecommunications, etc.) and systems development (windowing systems, compilers, etc.)
- DesignPatternsAsAPathToConceptualIntegrity . . . . 4 matches
During our discussions about the organization of design patterns there was a comment about the difficulty of identifying the “generative nature” of design patterns. This may be a good property to identify, for if we understood how design patterns are used in the design process, then their organization may not be far behind. Alexander makes a point that the generative nature of design patterns is one of the key benefits. In practice, on the software side, the generative nature seems to have fallen away and the more common approach for using design patterns is characterized as “when faced with problem xyz…the solution is…” One might say in software a more opportunistic application of design patterns is prevalent over a generative use of design patterns.
This is what Brooks wrote 25 years ago. "… Conceptual integrity is the most important consideration in system design."[Brooks 86] He continues: “The dilemma is a cruel one. For efficiency and conceptual integrity, one prefers a few good minds doing design and construction. Yet for large systems one wants a way to bring considerable manpower to bear, so that the product can make a timely appearance. How can these two needs be reconciled?”
One approach would be to identify and elevate a single overriding quality (such as adaptability or isolation of change) and use that quality as a foundation for the design process. If this overriding quality were one of the goals or even a specific design criteria of the process then perhaps the “many” could produce a timely product with the same conceptual integrity as “a few good minds.” How can this be accomplished and the and at least parts of the “cruel dilemma” resolved?
하나의 어프로치는 정의, 가장 최우선의 중요한 특질을 상승시킨다. (어뎁터빌리티나 변화에 대한 분리) 그리고 이 퀄리티들들을 디자인 프로세스의 설립의 용도로 이용할 수 있다. 만일 이 최우선의 특징이 프로세스의 목적이나 구체적 디자인 분류의 하나라면 아마 'many'는 같은 개념적 완전성을 "약간의 좋은 감정"으로서 적시에 프로덕트를 ..
· Will strong O-O design methods produce results for the “many” with the same conceptual integrity as “a few good minds.”
설득력있는 O-O 디자인 메소드들이 "a few good minds" 처럼 같은 개념적 완전성을 가진 "many" 를 에 대한 결과물을 만들어낼 것인가?
· How does it meet this objective?
The dilemma is a cruel one. For efficiency and conceptual integrity, one prefers a few good minds doing design and construction. Yet for large systems one wants a way to bring considerable manpower to bear, so that the product can make a timely appearance. How can these two needs be reconciled?
- FortuneCookies . . . . 4 matches
* Many pages make a thick book.
* You will step on the soil of many countries.
* Show your affection, which will probably meet with pleasant response.
* How sharper than a hound's tooth it is to have a thankless serpent.
* It's not reality that's important, but how you percieve things.
* Men seldom show dimples to girls who have pimples.
* How you look depends on where you go.
* Many changes of mind and mood; do not hesitate too long.
* You will have good luck and overcome many hardships.
* Be careful how you get yourself involved with persons or situations that can't bear inspection.
* Sin has many tools, but a lie is the handle which fits them all.
- HowToStudyDesignPatterns . . . . 4 matches
''The other thing I want to underscore here is how to go about reading Design Patterns, a.k.a. the "GoF" book. Many people feel that to fully grasp its content, they need to read it sequentially. But GoF is really a reference book, not a novel. Imagine trying to learn German by reading a Deutsch-English dictionary cover-to-cover;it just won't work! If you want to master German, you have to immerse yourself in German culture. You have to live German. The same is true of design patterns: you must immerse yourself in software development before you can master them. You have to live the patterns.
* 패턴이 어떻게 생성되었는지 그 과정을 보여주지 못한다. 즉, 스스로 패턴을 만들어내는 데에 전혀 도움이 안된다. (NoSmok:LearnHowTheyBecameMasters)
see also HowToStudyRefactoring, HowToStudyXp
- InvestMulti - 09.22 . . . . 4 matches
quantity = input('How Many do want to buy this item ? ')
quantity = input('How Many do want to buy this item ? ')
- TFP예제/WikiPageGather . . . . 4 matches
self.assertEquals (self.pageGather.GetPageNamesFromPage (), ["LearningHowToLearn", "ActiveX", "Python", "XPInstalled", "TestFirstProgramming", "한글테스트", "PrevFrontPage"])
'["LearningHowToLearn"]\n\n\n=== C++ ===\n["ActiveX"]\n\n' +
pagename : LearningHowToLearn
filename : LearningHowToLearn
- ToyProblems . . . . 4 matches
* HTDP (How To Design Programs) http://www.htdp.org/
* HowToSolveIt
* How to Prove it
* How to Read and Do Proofs
- TwistingTheTriad . . . . 4 matches
One example of this deficiency surfaced in SmalltalkWorkspace widget. This was originally designed as a multiline text-editing component with additional logic to handle user interface commands such as Do-it, Show-it, Inspect-it etc. The view itself was a standard Windows text control and we just attached code to it to handle the workspace functionality. However, we soon discovered that we also wanted to have a rich text workspace widget too. Typically the implementation of this would have required the duplication of the workspace logic from the SmalltalkWorkspace component or, at least, an unwarranted refactoring session. It seemed to us that the widget framework could well do with some refactoring itself!
In MVC, most of the application functionality must be built into a model class known as an Application Model. It is the reponsibility of the application model to be the mediator between the true domain objects and the views and their controllers. The views are responsible for displaying the domain data while the controller handle the raw usr gestures that will eventually perform action on this data. So the application model typically has method to perform menu command actions, push buttons actions and general validation on the data that it manages. Nearly all of the application logic will reside in the application model classes. However, because the application model's role is that of a go-between, it is at times necessary for it to gain access to the user interface directly but, because of the Observer relationship betweeen it and the view/controller, this sort of access is discouraged.
For example, let's say one wants to explicitly change the colour of one or more views dependent on some conditions in the application model. The correct way to do this in MVC would be to trigger some sort of event, passing the colour along with it. Behaviour would then have to be coded in the view to "hang off" this event and to apply the colour change whenever the event was triggered. This is a rather circuitous route to achieving this simple functionality and typically it would be avoided by taking a shoutcut and using #componentAt : to look up a particular named view from the application model and to apply the colour change to the view directly. However, any direct access of a view like this breaks the MVC dictum that the model should know nothing about the views to which it is connected. If nothing else, this sort of activity surely breaks the possibility of allowing multiple views onto a model, which must be the reason behind using the Observer pattern in MVC in the first place.
One significant difference in MVP is the removal of the controller. Instead, the view is expected to handle the raw user interface events generated by the operating system (in Windows these come in as WM_xxxx messages) and this way of working fits more naturally into the style of most modern operating systems. In some cases, as a TextView, the user input is handled directly by the view and used to make changes to the model data. However, in most cases the user input events are actually routed via the presenter and it is this which becomes responsible for how the model gets changed.
While it is the view's responsibility to display model data it is the presenter that governs how the model can be manipulated and changed by the user interface. This is where the heart of an application's behaviour resides. In many ways, a MVP presenter is equivalent to the application model in MVC; most of the code dealing with how a user interface works is built into a presenter class. The main difference is that a presenter is ''directly'' linked to its associated view so that the two can closely collaborate in their roles of supplying the user interface for a particular model.
- UML . . . . 4 matches
In software engineering, Unified Modeling Language (UML) is a non-proprietary, third generation modeling and specification language. However, the use of UML is not restricted to model software. It can be used for modeling hardware (engineering systems) and is commonly used for business process modeling, organizational structure, and systems engineering modeling. The UML is an open method used to specify, visualize, construct, and document the artifacts of an object-oriented software-intensive system under development. The UML represents a compilation of best engineering practices which have proven to be successful in modeling large, complex systems, especially at the architectural level.
This diagram describes the functionality of the (simple) Restaurant System. The Food Critic actor can Eat Food, Pay for Food, or Drink Wine. Only the Chef Actor can Cook Food. Use Cases are represented by ovals and the Actors are represented by stick figures. The box defines the boundaries of the Restaurant System, i.e., the use cases shown are part of the system being modelled, the actors are not.
The OMG defines a graphical notation for [[use case]]s, but it refrains from defining any written format for describing use cases in detail. Many people thus suffer under the misapprehension that a use case is its graphical notation; when in fact, the true value of a use case is the written description of scenarios regarding a business task.
This diagram describes the structure of a simple Restaurant System. UML shows [[Inheritance_(computer_science)|Inheritance]] relationships with a [[triangle]]; and containers with [[rhombus|diamond shape]]. Additionally, the role of the relationship may be specified as well as the cardinality. The Restaurant System has any number of Food dishes(*), with one Kitchen(1), a Dining Area(contains), and any number of staff(*). All of these objects are associated to one Restaurant.
Above is the collaboration diagram of the (simple) Restaurant System. Notice how you can follow the process from object to object, according to the outline below:
However, collaboration diagrams use the free-form arrangement of objects and links as used in Object diagrams. In order to maintain the ordering of messages in such a free-form diagram, messages are labeled with a chronological number and placed near the link the message is sent over. Reading a Collaboration diagram involves starting at message 1.0, and following the messages from object to object.
This activity diagram shows the actions that take place when completing a (web) form.
Deployment diagrams serve to model the hardware used in system implementations and the associations between those components. The elements used in deployment diagrams are nodes (shown as a cube), components (shown as a rectangular box, with two rectangles protruding from the left side) and associations.
This deployment diagram shows the hardware used in a small office network. The application server (node) is connected to the database server (node) and the database client (component) is installed on the application server. The workstation is connected (association) to the application server and to a printer.
At the same time, UML is often considered to have become too bloated, and fine-grained in many aspects. Details which are best captured in source code are attempted to be captured using UML notation. The [[80-20 rule]] can be safely applied to UML: a small part of UML is adequate for most of the modeling needs, while many aspects of UML cater to some specialized or esoteric usages.
(However, the comprehensive scope of UML 2.0 is appropriate for [[model-driven architecture]].)
- 지금그때/OpeningQuestion . . . . 4 matches
Pragmatic Programmers의 [http://www.pragmaticprogrammer.com/talks/HowToKeepYourJob/HowToKeepYourJob.htm How To Keep Your Job]을 강력 추천합니다. --JuNe
같은 주제 읽기(see HowToReadIt)를 하기에 도서관만한 곳이 없습니다. 그 경이적인 체험을 꼭 해보길 바랍니다. 그리고 도서신청제도를 적극적으로 활용하세요. 학생 때는 돈이 부족해서 책을 보지 못하는 경우도 있는데, 그럴 때에 사용하라고 도서신청제도가 있는 것입니다. --JuNe
- FocusOnFundamentals . . . . 3 matches
learn how to apply what they have been taught. I did learn a lot about the technology of that day in
The many good ideas that underlie these approaches and tools must be taught. Laboratory exercises
to experiment with some new ones. However, we must remember that these topics are today's
the lectures. Many programmes lose sight of the fact that learning a particular system or language
I would advise students to pay more attention to the fundamental ideas rather than the latest technology. The technology will be out-of-date before they graduate. Fundamental ideas never get out of date. However, what worries me about what I just said is that some people would think of Turing machines and Goedel's theorem as fundamentals. I think those things are fundamental but they are also nearly irrelevant. I think there are fundamental design principles, for example structured programming principles, the good ideas in "Object Oriented" programming, etc.
- HowManyZerosAndDigits/문보창 . . . . 3 matches
// no10061 - How many zeros and how many digits?
double nDigit; // how many digits?
int nZero; // how many zeros?
[HowManyZerosAndDigits] [문보창]
- MindMapConceptMap . . . . 3 matches
How To Read a Book 과 같은 책에서도 강조하는 내용중에 '책을 분류하라' 와 '책의 구조를 파악하라'라는 내용이 있다. 책을 분류함으로서 기존에 접해본 책의 종류와 비슷한 방법으로 접근할 수 있고, 이는 시간을 단축해준다. 일종의 知道랄까. 지식에 대한 길이 어느정도 잡혀있는 곳을 걸어가는 것과 수풀을 해치며 지나가는 것은 분명 그 속도에서 차이가 있을것이다.
관련 자료 : 'Learning How To Learn', 'Learning, Creating and Using Knowledge - Concept Maps as Facilitative Tools in Schools and Corporations' (Joseph D. Novak)
See Also ["HowToBuildConceptMap"]
- OpenGL스터디_실습 코드 . . . . 3 matches
* How to use :
* How to use :
* How to use :
- SmalltalkBestPracticePatterns/DispatchedInterpretation . . . . 3 matches
'''''How can two objects cooperate when one wishes to conceal its representation ? '''''
Encoding is inevitable in programming. At some point you say, "Here is some information. How am I going to represent it?" This decision to encode information happens a hundred times a day.
Back in the days when data was separated from computation, and seldom the twain should meet, encoding decisions were critical. Any encoding decision you made was propagated to many different parts of the computation. If you got the encoding wrong, the cost of change was enormous. The longer it took to find the mistake, the more ridiculous the bill.
Objects change all this. How you distribute responsibility among objects is the critical decision, encoding is a distant second. For the most part, in well factored programs, only a single object is interested in a piece of information. That object directly references the information and privately performs all the needed encoding and decoding.
Sometimes, however, information in one object must influence the behavior of another. When the uses of the information are simple, or the possible choices based on the information limited, it is sufficient to send a message to the encoded object. Thus, the fact that boolean values are represented as instances of one of two classes, True and False, is hidden behind the message #ifTrue:ifFalse:.
Sets interact with their elements like this. Regardless of how an object is represented, as long it can respond to #=and #hash, it can be put in a Set.
When there are many different types of information to be encoded, and the behavior of clients changes based on the information, these simple strategies won't work. The problem is that you don't want each of a hundred clients to explicitly record in a case statement what all the types of information are.
For example, consider a graphical Shape represented by a sequence of line, curve, stroke, and fill commands. Regardless of how the Shape is represented internally, it can provide a message #commandAt: anInteger that returns a Symbol representing the command and #argumentsAt: anInteger that returns an array of arguments. We could use these messages to write a PostScriptShapePrinter that would convert a Shape to PostScript:
- CubicSpline/1002/test_NaCurves.py . . . . 2 matches
def testMany(self):
def testSubBasedFunctionMany(self):
- Debugging . . . . 2 matches
* [http://wiki.kldp.org/wiki.php/HowToBeAProgrammer?action=highlight&value=%B5%F0%B9%F6%B1%EB#s-2.1.1 kldp_HowToBeAProgrammer]
- EnglishSpeaking/TheSimpsons/S01E02 . . . . 2 matches
Marge : All right. Mmm. How about "he"? Two points. Your turn, dear.
Homer : Hmm. How could anyone make a word out of these lousy letters?
Homer : I'll show you a big, dumb, balding ape!
- Gof/State . . . . 2 matches
이 방법은 HowDraw [Joh92]와 Unidraw [VL90] drawing editor 프레임워크에 이용되었다. 이는 클라이언트로 하여금 새로운 종류의 tool들을 쉽게 정의할 수 있도록 해준다. HowDraw 에서 DrawingController 클래스는 currentTool 객체에게 request를 넘긴다. UniDraw에서는 각각 Viewer 와 Tool 클래스가 이와 같은 관계를 가진다. 다음의 클래스 다이어그램은 Tool 과 DrawingController 인터페이스에 대한 설명이다.
- HowBigIsIt? . . . . 2 matches
=== HowBigIsIt? ===
|| 하기웅 || C++ || 완전 틀렸음ㅋㅋ || [HowBigIsIt?/하기웅] ||
- HowManyPiecesOfLand?/문보창 . . . . 2 matches
[HowManyPiecesOfLand?]
- HowManyZerosAndDigits/허아영 . . . . 2 matches
//HowManyZerosAndDigits
- HowToDiscussIt . . . . 2 matches
'''Separate What From How'''
* NoSmok:HowToMakeMeetingsWork
- HowToStudyDataStructureAndAlgorithms . . . . 2 matches
알고리즘을 공부하면 큰 줄기들을 알아야 합니다. 개별 테크닉들도 중요하지만 "패러다임"이라고 할만한 것들을 알아야 합니다. 그래야 알고리즘을 상황에 맞게 마음대로 응용할 수 있습니다. 또, 자신만의 분류법을 만들어야 합니다. (see also HowToReadIt Build Your Own Taxonomy) 구체적인 문제들을 케이스 바이 케이스로 여럿 접하는 동안 그냥 지나쳐 버리면 개별자는 영원히 개별자로 남을 뿐입니다. 비슷한 문제들을 서로 묶어서 일반화를 해야 합니다. (see also DoItAgainToLearn)
see also ["HowToStudyDesignPatterns"]
- HowToStudyRefactoring . . . . 2 matches
see also ["HowToStudyDesignPatterns"]
* Separate The What From The How : "어떻게"와 "무엇을"을 분리하도록 하라. 어떤 리팩토링이 창발하는가?
- XMLStudy_2002/XML+CSS . . . . 2 matches
<HTML:A href="http://msdn.microsoft.com/xml/xslguide/browsing-css.asp">How to Write a CSS StyleSheet for Browsing XML</HTML:A>
How to Write a CSS Style Sheet for Browsing XML</HTML:A>
- ZP도서관 . . . . 2 matches
|| HOW TO SOLVE IT || .............. || erunc0 || ? ||
|| Learning How To Learn || Joseph D. Novak || Cambridge University Press || 도서관 소장 || 학습기법관련 ||
|| How To Read a Book || Adler, Morimer Jero || Simon and Schuster || 도서관 소장(번역판 '논리적독서법' 도서관 소장, ["1002"] 소유. 그 외 번역판 많음) || 독서기법관련 ||
- [Lovely]boy^_^/EnglishGrammer/PresentPerfectAndPast . . . . 2 matches
Yet = until now. It shows that the speaker is expecting something to happen. Use yet only in questions and negative sentences.
== Unit11. How long have you (been) ...? ==
== Unit12. For and since, When ...?, and How long ...? ==
- callusedHand . . . . 2 matches
''DeleteMe) 처음 독서 방법에 대한 책에 대해 찾아봤었을때 읽었었던 책입니다. 당연한 말을 하는 것 같지만, 옳은 말들이기 때문에 당연한 말을 하는 교과서격의 책이라 생각합니다. 범우사꺼 얇은 책이라면 1판 번역일 것이고, 2판 번역과 원서 (How To Read a Book)도 도서관에 있습니다. --석천''
''(move to somewhere appropriate plz) 논리학 개론 서적으로는 Irving Copi와 Quine의 서적들(특히 Quine의 책은 대가의 면모를 느끼게 해줍니다), Smullyan의 서적들을 권하고, 논리학에서 특히 전산학과 관련이 깊은 수리논리학 쪽으로는 Mendelson이나 Herbert Enderton의 책을 권합니다. 또, 증명에 관심이 있다면 How to Prove It을 권합니다. 대부분 ["중앙도서관"]에 있습니다. (누가 신청했을까요 :) ) --JuNe''
- 기술적인의미에서의ZeroPage . . . . 2 matches
For example, the MOS Technology 6502 has only six non-general purpose registers. As a result, it used the zero page extensively. Many instructions are coded differently for zero page and non-zero page addresses:
The above two instructions both do the same thing; they load the value of $00 into the A register. However, the first instruction is only two bytes long and also faster than the second instruction. Unlike today's RISC processors, the 6502's instructions can be from one byte to three bytes long.
- 데블스캠프2005/java . . . . 2 matches
The Stealth Project was soon renamed to the Green Project with James Gosling and Mike Sheridan joining Patrick Naughton. They, together with some other engineers, began work in a small office on Sand Hill Road in Menlo Park, California to develop a new technology. The team originally considered C++ as the language to use, but many of them as well as Bill Joy found C++ and the available APIs problematic for several reasons.
Their platform was an embedded platform and had limited resources. Many members found that C++ was too complicated and developers often misused it. They found C++'s lack of garbage collection to also be a problem. Security, distributed programming, and threading support was also required. Finally, they wanted a platform that could be easily ported to all types of devices.
Like many stealth projects working on new technology, the team worked long hours and by the summer of 1992, they were able to demo portions of the new platform including the Green OS, Oak the language, the libraries, and the hardware. Their first attempt focused on building a PDA-like device having a highly graphical interface and a smart agent called Duke to assist the user.
In November of that year, the Green Project was spun off to become a wholly owned subsidiary of Sun Microsystems: FirstPerson, Inc. The team relocated to Palo Alto. The FirstPerson team was interested in building highly interactive devices and when Time Warner issued an RFP for a set-top box, FirstPerson changed their target and responded with a proposal for a set-top box platform. However, the cable industry felt that their platform gave too much control to the user and FirstPerson lost their bid to SGI. An additional deal with The 3DO Company for a set-top box also failed to materialize. FirstPerson was unable to generate any interest within the cable TV industry for their platform. Following their failures, the company, FirstPerson, was rolled back into Sun.
- 문제풀이게시판 . . . . 2 matches
* NoSmok:HowToSolveIt
see also HowToStudyDataStructureAndAlgorithms
- 알고리즘2주숙제 . . . . 2 matches
1. (Warm up) An eccentric collector of 2 x n domino tilings pays $4 for each vertical domino and $1 for each horizontal domino. How many tiling are worth exactly $m by this criterion? For example, when m = 6 there are three solutions.
4. (Homework exercises) How many spanning trees are in an n-wheel( a graph with n "outer" verices in a cycle, each connected to an (n+1)st "hub" vertex), when n >= 3?
- 정모/2012.1.20 . . . . 2 matches
* [김태진] 학우의 '''How to live SMART?''' How to use Camera?
- 정모/2012.4.2 . . . . 2 matches
* 위키에서 이런걸 발견했다. [http://wiki.zeropage.org/wiki.php/HowToStudyInGroups HowToStudyInGroups] 링크의 제목이 슬프다 - [서지혜]
- 제12회 한국자바개발자 컨퍼런스 후기 . . . . 2 matches
|| 15:00 ~ 15:50 || 스타트업을위한 Rapid Development (양수열) || 하둡 기반의 규모 확장성있는 트래픽 분석도구 (이연희) || 초보자를 위한 분산 캐시 활용 전략 (강대명) || Venture Capital & Start-up Investment (이종훈-벤처캐피탈협회) || How to deal with eXtream Applications? (최홍식) || SW 융합의 메카 인천에서 놀자! || 섹시한 개발자 되기 2.0 beta (자바카페 커뮤니티) ||
세 번째로 들은 것이 Track 5의 How to deal with eXtream Application이었는데.. 뭔가 하고 들었는데 들으면서 왠지 컴구 시간에 배운 것이 연상이 되었던 시간이었다. 다만 컴구 시간에 배운 것은 컴퓨터 내부에서 CPU에서 필요한 데이터를 빠르게 가져오는 것이었다면 이것은 서버에서 데이터를 어떻게 저장하고 어떻게 가져오는 것이 안전하고 빠른가에 대하여 이야기 하는 시간이었다.
- 2006김창준선배창의세미나 . . . . 1 match
= Play With Many Boxes =
- 2010Python . . . . 1 match
* 교재 : How to think like a computer scientist
- ASXMetafile . . . . 1 match
o ICON: The logo appears as an icon on the display panel, next to the title of the show or clip.
* How to define the path of source:
<Abstract>: This text will show up as a Tooltip and in the Properties dialog box
<Title> Global title of the show </Title>
<Ref href="MMS://netshow.microsoft.com/ms/sbnasfs/wtoc.asf" />
<Ref href="MMS://netshow.microsoft.com/ms/sbnasfs/wcc.asf" />
* [http://msdn.microsoft.com/downloads/samples/internet/imedia/netshow/simpleasx/default.asp MSDN Online Samples : Simple ASX] - [DeadLink]
- AirSpeedTemplateLibrary . . . . 1 match
However, in making Airspeed's syntax identical to that of Velocity, our goal is to allow Python programmers to prototype, replace or extend Java code that relies on Velocity.
- C/C++어려운선언문해석하기 . . . . 1 match
원문 : How to interpret complex C/C++ declarations (http://www.codeproject.com/cpp/complex_declarations.asp)
- C99표준에추가된C언어의엄청좋은기능 . . . . 1 match
The new variable-length array (VLA) feature is partially available. Simple VLAs will work. However, this is a pure coincidence; in fact, GNU C has its own variable-length array support. As a result, while simple code using variable-length arrays will work, a lot of code will run into the differences between the older GNU C support for VLAs and the C99 definition. Declare arrays whose length is a local variable, but don't try to go much further.
- CppUnit . . . . 1 match
[http://janbyul.com/moin/moin.cgi/CppUnit/HowTo/Kor 이곳]에 VS2005용 설정방법을 간단하게 정리해둠. - 임인택
- DataStructure . . . . 1 match
see also HowToStudyDataStructureAndAlgorithms
- DesignPattern2006 . . . . 1 match
* [HowToStudyDesignPatterns]
- DesignPatterns . . . . 1 match
see also [HowToStudyDesignPatterns], [DoWeHaveToStudyDesignPatterns]
- DesignPatterns/2011년스터디/1학기 . . . . 1 match
* HowToStudyDesignPatterns?
- DoItAgainToLearn . . . . 1 match
George Polya는 자신의 책 NoSmok:HowToSolveIt 에서 이런 말을 합니다:
- DocumentObjectModel . . . . 1 match
DOM API 쓰는 코드와 SAX API 쓰는 코드는 [http://www.python.or.kr/pykug/XML_bf_a1_bc_ad_20_c7_d1_b1_db_20_c3_b3_b8_ae_c7_cf_b1_e2 XML에서 한글 처리하기] 페이지중 소스코드를 참조. XPath 는 PyKug:HowToUseXPath 를 참조. --[1002]
- EnglishSpeaking/2012년스터디 . . . . 1 match
= How to =
- EnglishSpeaking/TheSimpsons/S01E03 . . . . 1 match
Lisa : How 'bout this? Supervising technician at the toxic waste dump.
- ExploringWorld/20040315-새출발 . . . . 1 match
* Tomcat 설치 port 8080, How To Program Java(학교 교재)의 뒷부분에 JSP 부분을 참고하였다.
- ExtremeProgramming . . . . 1 match
See Also HowToStudyXp , ["XpQuestion"]
- GTK+ . . . . 1 match
GTK+ is free software and part of the GNU Project. However, the licensing terms for GTK+, the GNU LGPL, allow it to be used by all developers, including those developing proprietary software, without any license fees or royalties.
gtk_widget_show(button);
gtk_widget_show(window);
- Garbage collector for C and C++ . . . . 1 match
# the GC process. This is no less correct than many malloc
# impact. However, it is dangerous for many not-quite-ANSI C
# to determine how particular or randomly chosen objects are reachable
# don't know how to retrieve arguments on the platform.
- Gof/FactoryMethod . . . . 1 match
You can avoid this by being careful to access products solely through accessor operations that create the product on demand. Instead of creating the concrete product in the constructor, the constructor merely initializes it to 0. The accessor returns the product. But first it checks to make sure the product exists, and if it doesn't, the accessor creates it. This technique is sometimes called lazy initialization. The following code shows a typical implementation:
Prototypes (117) don't require subclassing Creator. However, they often require an Initialize operation on the Product class. Creator uses Initialize to initialize the object. Factory Method doesn't require such an operation.
- Header 정의 . . . . 1 match
== How ==
- HierarchicalDatabaseManagementSystem . . . . 1 match
A hierarchical database is a kind of database management system that links records together in a tree data structure such that each record type has only one owner (e.g., an order is owned by only one customer). Hierarchical structures were widely used in the first mainframe database management systems. However, due to their restrictions, they often cannot be used to relate structures that exist in the real world.
Hierarchical relationships between different types of data can make it very easy to answer some questions, but very difficult to answer others. If a one-to-many relationship is violated (e.g., a patient can have more than one physician) then the hierarchy becomes a network.
- HowToBuildConceptMap . . . . 1 match
How To Build a Concept Map
* Concept maps could be made in many different forms for the same set of concepts. There is no one way to draw a concept map. As your understanding of relationships between concepts changes, so will your maps.
- HowToReadIt . . . . 1 match
NoSmok:HowToReadIt
- Ieee754Standard . . . . 1 match
* [http://www.cs.berkeley.edu/~wkahan/JAVAhurt.pdf How JAVA's Floating-Point Hurts Everyone Everywhere]
- JTDStudy . . . . 1 match
* What is JUnit? How use this?
- JavaStudy2004 . . . . 1 match
* 추천도서 - Java HowToProgram - Deitel사. 2학년 전공 JavaProgrammingClass에서 교재로 사용하는 책. 간단하고 쉽다. 자바를 처음 시작하는 이에게 추천도서
- KDPProject . . . . 1 match
*["HowToStudyDesignPatterns"] - DP 를 공부하기 전에 생각해볼 수 있는 이야기들.
- Knapsack . . . . 1 match
처음부터 단박에 이 문제를 푸는 것보다 조금 더 제한적이고 쉬운 문제에서 일반적이고 어려운 문제로 점진적으로 진행해 나가는 것은 어떨까요. NoSmok:HowToSolveIt 에서 소개하는 문제 해결 테크닉 중 하나이기도 하죠. 훨씬 더 높은 교육적 효과를 기대할 수 있지 않을까 합니다.
- Kongulo . . . . 1 match
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
help='How deep to follow links from BASEURLs (default 0, '
- LightMoreLight/허아영 . . . . 1 match
How do I code this contents??
I learned how to solve the Number of n's measure.. at a middle school.
- LinearAlgebraClass . . . . 1 match
길버트 스트랭은 선형대수학 쪽에선 아주 유명한 사람으로, 그이의 ''Introduction to Linear Algebra''는 선형대수학 입문 서적으로 정평이 나있다. 그의 MIT 수업을 이토록 깨끗한 화질로 "공짜로" 한국 안방에 앉아서 볼 수 있다는 것은 축복이다. 영어 듣기 훈련과 수학공부 두마리를 다 잡고 싶은 사람에게 강력 추천한다. 선형 대수학을 들었던(그리고 학기가 끝나고 책으로 캠프화이어를 했던) 사람이라면 더더욱 추천한다. (see also HowToReadIt 같은 대상에 대한 다양한 자료의 접근) 대가는 기초를 어떻게 가르치는가를 유심히 보라. 내가 학교에서 선형대수학 수강을 했을 때, 이런 자료가 있었고, 이런 걸 보라고 알려주는 사람이 있었다면 학교 생활이 얼마나 흥미진지하고 행복했을지 생각해 보곤 한다. --JuNe
- LispLanguage . . . . 1 match
* [http://dept-info.labri.fr/~strandh/Teaching/Programmation-Symbolique/Common/David-Lamkins/contents.html Successful Lisp:How to Understand and Use Common Lisp] - 책인듯(some 에 대한 설명 있음)
- MoinMoinDiscussion . . . . 1 match
'''Q''': How do you inline an image stored locally? (e.g. ../wiki-moimoin/data/images/picture.gif)
- MoreEffectiveC++/Appendix . . . . 1 match
For a more general reference on the language, the standard library, and how to apply it, there is no better place to look than the book by the man responsible for C++ in the first place: ¤ MEC++ Rec Reading, P10
If you're ready to move beyond the language itself and are interested in how to apply it effectively, you might consider my other book on the subject: ¤ MEC++ Rec Reading, P13
Each chapter in this book starts with some C++ software that has been published as an example of how to do something correctly. Cargill then proceeds to dissect — nay, vivisect — each program, identifying likely trouble spots, poor design choices, brittle implementation decisions, and things that are just plain wrong. He then iteratively rewrites each example to eliminate the weaknesses, and by the time he's done, he's produced code that is more robust, more maintainable, more efficient, and more portable, and it still fulfills the original problem specification. Anybody programming in C++ would do well to heed the lessons of this book, but it is especially important for those involved in code inspections. ¤ MEC++ Rec Reading, P21
One topic Cargill does not discuss in C++ Programming Style is exceptions. He turns his critical eye to this language feature in the following article, however, which demonstrates why writing exception-safe code is more difficult than most programmers realize: ¤ MEC++ Rec Reading, P22
I generally refer to this as "the LSD book," because it's purple and it will expand your mind. Coplien covers some straightforward material, but his focus is really on showing you how to do things in C++ you're not supposed to be able to do. You want to construct objects on top of one another? He shows you how. You want to bypass strong typing? He gives you a way. You want to add data and functions to classes as your programs are running? He explains how to do it. Most of the time, you'll want to steer clear of the techniques he describes, but sometimes they provide just the solution you need for a tricky problem you're facing. Furthermore, it's illuminating just to see what kinds of things can be done with C++. This book may frighten you, it may dazzle you, but when you've read it, you'll never look at C++ the same way again. ¤ MEC++ Rec Reading, P27
Carroll and Ellis discuss many practical aspects of library design and implementation that are simply ignored by everybody else. Good libraries are small, fast, extensible, easily upgraded, graceful during template instantiation, powerful, and robust. It is not possible to optimize for each of these attributes, so one must make trade-offs that improve some aspects of a library at the expense of others. Designing and Coding Reusable C++ examines these trade-offs and offers down-to-earth advice on how to go about making them. ¤ MEC++ Rec Reading, P30
This book provides an overview of the ideas behind patterns, but its primary contribution is a catalogue of 23 fundamental patterns that are useful in many application areas. A stroll through these pages will almost surely reveal a pattern you've had to invent yourself at one time or another, and when you find one, you're almost certain to discover that the design in the book is superior to the ad-hoc approach you came up with. The names of the patterns here have already become part of an emerging vocabulary for object-oriented design; failure to know these names may soon be hazardous to your ability to communicate with your colleagues. A particular strength of the book is its emphasis on designing and implementing software so that future evolution is gracefully accommodated (see Items 32 and 33). ¤ MEC++ Rec Reading, P36
Items 9, 10, 26, 31 and 32 attest to the remarkable utility of the auto_ptr template. Unfortunately, few compilers currently ship with a "correct" implementation.1 Items 9 and 28 sketch how you might write one yourself, but it's nice to have more than a sketch when embarking on real-world projects. ¤ MEC++ auto_ptr, P2
Below are two presentations of an implementation for auto_ptr. The first presentation documents the class interface and implements all the member functions outside the class definition. The second implements each member function within the class definition. Stylistically, the second presentation is inferior to the first, because it fails to separate the class interface from its implementation. However, auto_ptr yields simple classes, and the second presentation brings that out much more clearly than does the first. ¤ MEC++ auto_ptr, P3
- OperatingSystemClass/Exam2002_2 . . . . 1 match
* If a memory reference takes 200 nanoseconds, how long does a paged memory reference take?
How many page faults would occur for the following replacement algorithm, assuming one, three, five, seven frames? Remember all frames are initially empty, so your first unique pages will all cost one fault each.
6. Consider a file currently consisting of 100 blocks. Assume that the file control block(and the index block, in the case of indexed allocation) is already in memory, Calculate how many disk I/O operations are required for contiguous, linked and indexed (single-level) allocation strategies, if for one block, the following conditions hold. In the contiguous allocation case, assume that there is no room to grow in the beginning, but there is room to grow in the end. Assume that the block information to be added in stored in memory.
- PPProject/Colume2Exercises . . . . 1 match
막힌다는 느낌이 들면, 문제를 다시 이해해본다. HowToSolveIt에서 나왔던 발제를 스스로 해본다. 이번에는 빼먹고 넘어간 조건이있는가?라는 발제를 빨리 했더라면 해결 할 수 있었을 것이다.
- PaintBox . . . . 1 match
* How To Program Java 6E
- PragmaticVersionControlWithCVS . . . . 1 match
|| ch4 || [PragmaticVersionControlWithCVS/HowTo] ||
- PragmaticVersionControlWithCVS/CommonCVSCommands . . . . 1 match
M SourceCode/HowTo.tip
- PragmaticVersionControlWithCVS/Getting Started . . . . 1 match
|| [PragmaticVersionControlWithCVS/WhatIsVersionControl] || [PragmaticVersionControlWithCVS/HowTo] ||
- PragmaticVersionControlWithCVS/HowTo . . . . 1 match
= How To =
- ProgrammingPartyAfterwords . . . . 1 match
각 팀별로 전지에 자신들의 디자인을 표현하고 모두에게 그 디자인에 대해 설명하는 식으로 발표를 하였다. 각 팀별 디자인의 특징을 볼 수 있었다. '뭘 잘못했느냐?'가 아니라 '어떻게 해야 잘할 수 있었을까?'와 같은 '올바른 질문'을 던짐으로써 더 배울 수 있다는 것을 확인할 수 있었다. 그리고 발표할때 What 과 How 를 분리하고 What 만을 전달해야 한다는 것이 중요하다는 것을 관찰할 수 있었다.
- REFACTORING . . . . 1 match
See Also HowToStudyRefactoring, Xper:RefactoringWorkbook
- ReadySet 번역처음화면 . . . . 1 match
* Templates for many common software engineering documents. Including:
These templates are not one-size-fits-all and they do not attempt to provide prescriptive guidance on the overall development process. We are developing a broad library of template modules for many purposes and processes. The templates may be filled out in a suggested sequence or in any sequence that fits your existing process. They may be easily customized with any text or HTML editor.
'''*How can users get started?'''
- RedThon . . . . 1 match
{{|Many programmes lose sight of the fact that learning a particular system or language is a means of learning something else, not an goal in itself.
- SchemeLanguage . . . . 1 match
* http://www.htdp.org/ - How To Design Programs. 비 전공자들을 위한 Scheme Language 책으로, 인터넷에 공개되어있다. 위의 PLT Scheme 을 인스톨하면 Help 탭에 HTDP 링크가 생긴다.
- SeminarHowToProgramItAfterwords . . . . 1 match
SeminarHowToProgramIt에 대한 감상, 후기, 각종 질답, 논의, ThreeFs.
- SmallTalk/강좌FromHitel/강의3 . . . . 1 match
* How many attempts did it take you to download this software?:
- TestDrivenDevelopmentByExample . . . . 1 match
개인적으로 TDD 중 빠른 테스트 통과를 위해 가짜 상수로 쌓아나갈때 어떻게 '중복' 이라 하여 ["Refactoring"] 할까 고민했었는데, 이전의 SeminarHowToProgramIt 에서의 예제 이후 이 문서에서의 예제가 깔끔하게 풀어주네요. 인제 한번 들여다 본 중이긴 하지만, 저자가 저자인 만큼 (KentBeck).~
- TopicMap . . . . 1 match
''Nice idea. But i would just make it the normal behavior for external links. That way you don't clutter MoinMoin with too many different features. --MarkoSchulz''
I plan to use [ ] with a consistent syntax for such things. How do you mean the external link thing? Including other web pages, or "only" other Wiki pages?
OK, for the simple stuff (i.e. local links), how about this:
- UbuntuLinux . . . . 1 match
[https://wiki.ubuntu.com/ThinClientHowtoNAT] 이 두 문서를 따라하다 보니 어느새 다른 컴퓨터에서 인터넷에 연결할 수 있는 것이 아닌가!
방법은 서버에서 서브도메인을 나눠주는 것이 좋겠는데, 아직 이건 잘 모르겠고 Samba를 통해 공유 폴더를 이용하는 수준까지 이르렀다. [http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#anon-example 따라하기]
[http://www.dougsparling.com/comp/howto/linux_java.html]
- Unicode . . . . 1 match
{{{In computing, Unicode provides an international standard which has the goal of providing the means to encode the text of every document people want to store on computers. This includes all scripts in active use today, many scripts known only by scholars, and symbols which do not strictly represent scripts, like mathematical, linguistic and APL symbols.
Establishing Unicode involves an ambitious project to replace existing character sets, many of them limited in size and problematic in multilingual environments. Despite technical problems and limitations, Unicode has become the most complete character set and one of the largest, and seems set to serve as the dominant encoding scheme in the internationalization of software and in multilingual environments. Many recent technologies, such as XML, the Java programming language as well as several operating systems, have adopted Unicode as an underlying scheme to represent text.
- WOWAddOn/2011년프로젝트/초성퀴즈 . . . . 1 match
HelloWoW_ShowMessage();
function HelloWoW_ShowMessage()
function HelloWoW_ShowMessage()
function HelloWoW_ShowMessage()
function HelloWoW_ShowMessage()
function HelloWoW_ShowMessage()
HelloWoW_ShowMessage(self)
function HelloWoW_ShowMessage(self)
How Often Is It Called
OnUpdate is not called on any hidden frames, only while they are shown on-screen. OnUpdate will also never be called on a virtual frame, but will be called on any frames that inherit from one.
- WikiSlide . . . . 1 match
* Creating documentation and slide shows ;)
== How do I navigate? ==
(!) If you discover an interesting format somewhere, just use the "raw" icon to find out how it was done.
* `TableOfContents` - show a local table of contents
== Wikiquette - how do I behave correctly? ==
* Follow the guidance of the Wiki used about how to name pages etc.
- WindowsTemplateLibrary . . . . 1 match
Being an unsupported library, WTL has little formal documentation. However, most of the API is a direct mirror of the standard Win32 calls, so the interface is familiar to most Windows programmers.|}}
- XMLStudy_2002/Encoding . . . . 1 match
Shuart Culshaw. "Towards a Truly WorldWide Web. How XML and Unicode are making it easier to publish multilingual
- XpWeek/준비물 . . . . 1 match
* HowToStudyExtremeProgramming
- ZeroPageEvents . . . . 1 match
|| 4.11. 2002 || ["SeminarHowToProgramIt"] || . || 세미나 & 진행 : ["JuNe"][[BR]] 참가 : 이선우, ["woodpage"], ["물푸"], ["1002"], ["상협"], ["[Lovely]boy^_^"], ["neocoin"], ["구근"], ["comein2"], ["zennith"], ["fnwinter"], ["신재동"], ["창섭"], ["snowflower"], ["이덕준"], 채희상, 임차섭, 김형용, 김승범, 서지원, 홍성두 [[BR]] 참관: ["최태호"], ["nautes"], ["JihwanPark"], 최유환, 이한주, 김정준, 김용기 ||
- ZeroPageServer/SubVersion . . . . 1 match
* Many improved APIs
- ZeroPageServer/old . . . . 1 match
* [http://www.robotstxt.org/wc/exclusion.html robot]규약 으로 엠파스의 침입을 막아야 한다. HowToBlockEmpas
- ZeroWiki/제안 . . . . 1 match
HowToEscapeFromMoniWiki
- [Lovely]boy^_^/Diary/12Rest . . . . 1 match
* I modify above sentence.--; I test GetAsyncKeyState(), but it's speed is same with DInput.--; How do I do~~~?
- [Lovely]boy^_^/Diary/2-2-1 . . . . 1 match
* ["EffectiveSTL"], HowToSolveIt(["신재동"]군이 꼬심) 빌림.
- [Lovely]boy^_^/EnglishGrammer/Passive . . . . 1 match
ex) How many babies are born every day?
B. Some verbs can have two objects(ex : give, ask, offer, pay, show, teach, tell)
A. ex) Henry is very old. Nobody knows exactly how old he is, but :
- [Lovely]boy^_^/ExtremeAlgorithmStudy . . . . 1 match
* ["HowToStudyDataStructureAndAlgorithms"]
- neocoin/Education . . . . 1 match
잘 가르치기 위해서는 기본적인 교육학 이론보다는 Cognitive Psychology(학습부분)와 실제 "훌륭한 교사"들의 방법을 설명한 책(예컨대 NoSmok:SuccessfulCollegeTeaching ), 그리고 학습 과정을 설명한 책(NoSmok:HowPeopleLearn )이 좋을 것이다. 또 성인 교육에 있어서는 Training, Coaching 관련 서적이 많은 도움이 된다. --JuNe
- wiz네처음화면 . . . . 1 match
= How to contact? =
* http://blog.empas.com/tobfreeman/13965830 , http://knowhow.interpark.com/shoptalk/qna/qnaContent.do?seq=96903
- 같은 페이지가 생기면 무슨 문제가 있을까? . . . . 1 match
무엇(What-손이 한 번 이라도 덜 가는 구조)인지는 알고, 이것은 저도 전제로 삼는 지향점 입니다. 이야기 할 발전적인 방향은 어떻게(How-그 구조로 어떻게 만들까?)를 논하는 것 이라 생각합니다. 제가 너무 함축적으로 글을 작성해서 풀어 씁니다.
- 권영기/web crawler . . . . 1 match
* http://coreapython.hosting.paran.com/howto/HOWTO%20Fetch%20Internet%20Resources%20Using%20urllib2.htm
* 문서 - http://wiki.wxpython.org/How%20to%20Learn%20wxPython
- 다이얼로그박스의 엔터키 막기 . . . . 1 match
== How to ==
- 데블스캠프2002/날적이 . . . . 1 match
* Scenario Driven 관계상 중간중간 실제 프로그램 구현시 어떻게 할것인가를 자주 언급되었다. 'What' 과 'How' 의 분리면에서는 두 사고과정이 왕복되는 점에서 효율성이 떨어진다고 생각한다.
- 데블스캠프2004/세미나주제 . . . . 1 match
* 자료구조 SeeAlso HowToStudyDataStructureAndAlgorithms, DataStructure StackAndQueue 뒤의 두 페이지들의 용어와 내용이 어울리지 않네요. 아, 일반 용어를 프로젝트로 시작한 페이지의 마지막 모습이군요. )
- 데블스캠프2010 . . . . 1 match
[HowToCodingWell] [SibichiSeminar]
- 데블스캠프2010/다섯째날/ObjectCraft . . . . 1 match
0. Why > How
- 데블스캠프2011/다섯째날/후기 . . . . 1 match
== 변형진/How To Write Code Well ==
* 코드 잘 짜는 법. 신경써야 할 부분을 최소한으로 줄이자. 필요한 것을 먼저 쓰고 구현은 나중에 한다. 자주, 많이. very very many many
- 데블스캠프2012/다섯째날/후기 . . . . 1 match
* [이재형] - 오버로딩이나, 탬플릿 까지는 어렵지 않게 이해했는데 그 뒤부터 클래스, 구조체, 생성자와 소멸자, 상속, 가상함수 등등 부족한게 많아서 정말 멘붕에 멘붕을 거듭했습니다. 그래도 정말정말 How에대한 관점으로 공부해야겠다는 필요성과 더불어 이번 방학 공부에 동기부여가 잘 될 것 같아서 좌절감만 드는 것이 아니였습니다. 좋은 어려움이였던 것 같습니다.
- 디자인패턴 . . . . 1 match
HowToStudyDesignPatterns 페이지를 참조하세요.
- 몸짱프로젝트 . . . . 1 match
SeeAlso [HowToStudyDataStructureAndAlgorithms] [DataStructure] [http://internet512.chonbuk.ac.kr/datastructure/data/ds1.htm 자료구조 정리]
- 박성현 . . . . 1 match
* [http://wiki.kldp.org/wiki.php/DocbookSgml/Ask-TRANS How To Ask Questions The Smart Way]
- 새싹교실/2012/세싹 . . . . 1 match
- http://www.codeproject.com/Articles/24415/How-to-read-dump-compare-registry-hives
- 송지원 . . . . 1 match
* [데블스캠프2011/다섯째날/How To Write Code Well/송지원, 성화수]
- 시간관리하기 . . . . 1 match
DeleteMe) 영어로 쓰려면 HowToManagement... 류가 되려나. -_-; 개인적으로 그리 치열하게 살지 않는 사람으로서 이런 페이지 글 적는게 좀 그렇지만. -_-; 일단 화두 제공용. 질문하기위해 연 페이지라고 생각하시길. --["1002"]
- 안혁준 . . . . 1 match
* [HowTo] 시리즈 집필
- 양쪽의 클래스를 참조 필요시 . . . . 1 match
== How to ==
- 영호의바이러스공부페이지 . . . . 1 match
002...........................How to modify viruses to avoid SCAN
- HOW TO MODIFY A VIRUS SO SCAN WON'T CATCH IT -
HOW TO CREATE NEW VIRUS STRAINS
THE FOLLOWING TAKES A SOMEWHAT KNOWING OF ASSEMBLER AND HOW IT WORKS!!!!!!
how to do this from debug.
- 영호의해킹공부페이지 . . . . 1 match
many are, a root shell will be spawned, giving full remote access.
A buffer is a block of computer memory that holds many instances of the same
Heeey, I gave it too many characters and it didn't crash. It worked. :) That
This will cover how to write your first program in assembly using DEBUG.COM as
(Now we start compiling our lil codey, awww how kewt;)
So now as another practical example, let's look at how we would hide a program
which wont show up in the windows task list.
Now for How to get mastercode for unlocking cellphones...
phone. Press * many times for "p" and "w".
- 위키로프로젝트하기 . . . . 1 match
* How - 목표를 위한 방법과 일정의 기록이다. Offline 또는 Online 상에서 한 일에 대한 ["ThreeFs"] 를 남겨라.
- 이영호/개인공부일기장 . . . . 1 match
☆ 앞으로 공부해야할 책들(사둔것) - Effective C++, More Effective C++, Exeptional C++ Style, Modern C++ Design, TCP/IP 네트워크 관리(출판사:O'Reilly), C사용자를 위한 리눅스 프로그래밍, Add-on Linux Kernel Programming, Physics for Game Developers(출판사:O'Reilly), 알고리즘(출판사:O'Reilly), Hacking Howto(Matt 저), Windows 시스템 실행 파일의 구조와 원리, C언어로 배우는 알고리즘 입문
- 일취집중후각법 . . . . 1 match
["Refactoring"]의 도를 얻기 위한 수련법의 하나. see also HowToStudyRefactoring
- 임시 . . . . 1 match
[http://www.cse.buffalo.edu/~rapaport/howtostudy.html How to study]
This section explains how to use REST (Representational State Transfer) to make requests through Amazon E-Commerce Service (ECS). REST is a Web services protocol that was created by Roy Fielding in his Ph.D. thesis (see Architectural Styles and the Design of Network-based Software Architectures for more details about REST).
- 재미있게공부하기 . . . . 1 match
''재미있는 것부터 하기''와 비슷하게 특정 부분을 고르고 그 놈을 집중 공략해서 공부하는 방법이다. 이 때 가능하면 여러개의 자료를 총 동원한다. 예를 들어 논리의 진리표를 공부한다면, 논리학 개론서 수십권을 옆에 쌓아놓고 인덱스를 보고 진리표 부분만 찾아읽는다. 설명의 차이를 비교, 관찰하라(부수적으로 좋은 책을 빨리 알아채는 공력이 쌓인다). 대가는 어떤 식으로 설명하는지, 우리나라 번역서는 얼마나 개판인지 등을 살피다 보면 어느새 자신감이 붙고(최소한 진리표에 대해서 만큼은 빠싹해진다) 재미가 생긴다. see also HowToReadIt의 ''같은 주제 읽기''
- 정모 . . . . 1 match
See Also HowToDiscussIt
- 정모/2012.12.10 . . . . 1 match
* 저분들께 이 글을 보여드리고 싶다. [http://jimmyrim.com/159 Paul Graham의 How To Start a Startup], [http://www.jimmyrim.com/190 스타트업에서 일과 삶의 균형을 찾는 것은 맞지 않다.] 음.. 근데 저분들 스타트업 하려는거 맞나? - [서지혜]
- 졸업논문 . . . . 1 match
= How to =
- 찜질방원정대 . . . . 1 match
=== How to escape from invincible solo corps ===
- 캠이랑놀자 . . . . 1 match
|| 2 || 05.9.25 || [캠이랑놀자/050925] || DirectShow 개관. 뼈대 코드 구경. 간단한 캠영상 플레이 프로그램 만들기 || . ||
|| 13 || 06.1.13 || [캠이랑놀자/060113] 1시 || How to solve it using Image Processing (?) || . ||
* DirectShow 나 OpenCV 중 하나
- 파스칼삼각형/sksmsvlxk . . . . 1 match
cout << "How many lines?? : ";
Found 155 matching pages out of 7540 total pages (5000 pages are searched)
You can also click here to search title.
